Seamless and reliable chain of custody transfer over low power wireless protocol

ABSTRACT

Apparatuses and methods for providing change of custody signaling in a wireless sensor network are disclosed herein. In embodiments, an apparatus for providing transfer of custody signaling in a wireless sensor network (WSN) may be provided. The apparatus may include communications circuitry to interact with a cloud server to receive an instruction regarding a change of custody for at least one sensor node within a WSN, the at least one sensor node assigned to the apparatus for tracking, and the instruction may identify a second apparatus within the WSN to assume custody of the at least one sensor. The apparatus may further include a control unit coupled to the communications circuitry to signal the second apparatus and the at least one sensor node regarding the transfer of custody, wherein the signaling is over a wireless protocol of the WSN.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/598,156, filed May 17, 2017, entitled “SEAMLESS AND RELIABLE CHAIN OFCUSTODY TRANSFER OVER LOW POWER WIRELESS PROTOCOL”, the contents ofwhich is hereby incorporated by reference herein in its entirety for allpurposes.

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to the field ofwireless sensor networks (WSNs), and in particular to chain of custodytransfer communications in such wireless sensor networks.

BACKGROUND

Third party logistic companies and retail distributors need anend-to-end solution to monitor the condition and location of assetsduring all stages of shipment at configurable temporal resolutions. Inmost logistics and tracking applications, sensors on specific packagesneed to seamlessly move from one gateway (GW) network in, for example, awarehouse to another mobile GW network, for example, in a truck. Suchtransfers are generally managed by a cloud server, that communicates toeach GW. However, at locations where the cloud might be inaccessible,this poses a problem.

Conventionally, sensor modules equipped with GPS trackers are attachedto pieces of cargo, and tracked by a cloud-based system from end-to-end.This may be an expensive and cloud intensive approach, which relies oncontinual communications between smart tags and one or more cloudservers.

Moreover, it is noted that existing wireless sensor network protocolsrestrict scalability and demand greater radio activity than is oftenfeasible for dense low-power networks. Further issues arise from theinterdependence of software, hardware, and energy. For example, thewell-integrated ZigBee® PRO paired with a Contiki operating system has alarge and complex software stack, demanding greater memory, processing,and energy from the hardware. While alternatives to 2.4 GHz, such as theLoRa Alliance™ embrace lower carrier frequencies and channel hopping forlonger range, they also require larger antenna and lower data rates, aswell as existing infrastructure.

Thus, while conventional solutions may suit small-scale consumer needs,they exhibit costly overhead for next-generation, resource-limited,pervasive networks and scalable/dense Internet of Things (IoT).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example a system to provide asset tracking andchange of custody transfer communications in accordance with variousembodiments.

FIG. 2 illustrates an overview of the operational flow of a process foran example process flow for transfer of custody from a current gatewayto a new gateway, in accordance with various embodiments.

FIG. 3 illustrates an example process flow for a new gateway havingreceived a new set of nodes, in accordance with various embodiments.

FIG. 4 illustrates an example process flow for a gateway discovering“lost” nodes, in accordance with various embodiments.

FIG. 5A depicts an example association beacon that may be sent out by anew gateway, and example client responses that may be received, inaccordance with various embodiments.

FIG. 5B depicts magnified views of the association beacon and clientresponses, and the MAC payload of the association beacon, both shown inFIG. 5A.

FIG. 6 depicts an example beacon that may be sent to advise clients of achange in gateway ID and channel ID as part of a custody handoff ofthose clients from a current gateway to a new gateway, in accordancewith various embodiments.

FIG. 7 illustrates a block diagram of a computer device suitable forpracticing the present disclosure, in accordance with variousembodiments.

FIG. 8 illustrates an example computer-readable storage medium havinginstructions configured to practice aspects of the processes of FIGS.2-4, in accordance with various embodiments.

DETAILED DESCRIPTION

In embodiments, a reliable, optimum and elegant technique to implement achain of custody transfer of sensors between one gateway (GW) to anotherwithin a wireless sensor network (WSN) over a wireless protocol, whilethe goods to which the sensors are attached or associated with are stillin transit or operation, may be provided. In embodiments, the chain ofcustody transfers may be implemented with minimal to no manualintervention. Thus, various techniques in accordance with embodimentsherein allow for gateway to gateway (GW to GW) communication. Suchcommunication may often be more reliable while the cloud might beinaccessible. In embodiments, the chain of custody transfers may beimplemented by utilizing the periodic beacons from GWs—that areprimarily used for time synchronization of the network—to propagatecustody transfer configuration changes to respective sensor nodes.

Additionally, in embodiments, the chain of custody transfers may beperformed by ensuring that no sensors/nodes are stranded or unassociatedfrom a GW at any point in time. Techniques according to variousembodiments may be implemented in a power optimized manner while stillmaintaining high reliability and ease of use.

In the description to follow, reference is made to the accompanyingdrawings which form a part hereof wherein like numerals designate likeparts throughout, and in which is shown by way of illustrationembodiments that may be practiced. It is to be understood that otherembodiments may be utilized and structural or logical changes may bemade without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Operations of various methods may be described as multiple discreteactions or operations in turn, in a manner that is most helpful inunderstanding the claimed subject matter. However, the order ofdescription should not be construed as to imply that these operationsare necessarily order dependent. In particular, these operations may notbe performed in the order of presentation. Operations described may beperformed in a different order than the described embodiments. Variousadditional operations may be performed and/or described operations maybe omitted, split or combined in additional embodiments.

For the purposes of the present disclosure, the phrase “A and/or B”means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

Also, it is noted that embodiments may be described as a processdepicted as a flowchart, a flow diagram, a dataflow diagram, a structurediagram, or a block diagram. Although a flowchart may describe theoperations as a sequential process, many of the operations may beperformed in parallel, concurrently, or simultaneously. In addition, theorder of the operations may be re-arranged. A process may be terminatedwhen its operations are completed, but may also have additional stepsnot included in the figure(s). A process may correspond to a method, afunction, a procedure, a subroutine, a subprogram, and the like. When aprocess corresponds to a function, its termination may correspond to areturn of the function to the calling function and/or the main function.Furthermore, a process may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks may be stored in a machine or computer readable medium. A codesegment may represent a procedure, a function, a subprogram, a program,a routine, a subroutine, a module, program code, a software package, aclass, or any combination of instructions, data structures, programstatements, and the like.

As used hereinafter, including the claims, the term “circuitry”,including “communications circuitry” or “supporting circuitry” may referto, be part of, or include an Application Specific Integrated Circuit(ASIC), an electronic circuit, a processor (shared, dedicated, orgroup), and/or memory (shared, dedicated, or group) that execute one ormore software or firmware programs, a combinational logic circuit,and/or other suitable hardware components that provide the describedfunctionality and/or any combination of software, firmware or hardware.In some embodiments, the circuitry may implement, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules.

As used hereinafter, including the claims, the term “memory” mayrepresent one or more hardware devices for storing data, includingrandom access memory (RAM), magnetic RAM, core memory, read only memory(ROM), magnetic disk storage mediums, optical storage mediums, flashmemory devices and/or other machine readable mediums for storing data.The term “computer-readable medium” may include, but is not limited to,memory, portable or fixed storage devices, optical storage devices,wireless channels, and various other mediums capable of storing,containing or carrying instruction(s) and/or data.

As used hereinafter, including the claims, the term “computing platform”may be considered synonymous to, and may hereafter be occasionallyreferred to, as a computer device, computing device, client device orclient, mobile, mobile unit, mobile terminal, mobile station, mobileuser, mobile equipment, user equipment (UE), user terminal, machine-typecommunication (MTC) device, machine-to-machine (M2M) device, M2Mequipment (M2ME), Internet of Things (IoT) device, subscriber, user,receiver, etc., and may describe any physical hardware device capable ofsequentially and automatically carrying out a sequence of arithmetic orlogical operations, equipped to record/store data on a machine readablemedium, and transmit and receive data from one or more other devices ina communications network. Furthermore, the term “computing platform” mayinclude any type of electronic device, such as a cellular phone orsmartphone, a tablet personal computer, a wearable computing device, anautonomous sensor, personal digital assistants (PDAs), a laptopcomputer, a desktop personal computer, a video game console, a digitalmedia player, an in-vehicle infotainment (IVI) and/or an in-carentertainment (ICE) device, a vehicle-to-vehicle (V2V) communicationsystem, a vehicle-to-everything (V2X) communication system, a handheldmessaging device, a personal data assistant, an electronic book reader,an augmented reality device, and/or any other like electronic device.

As used hereinafter, including the claims, the term “link” or“communications link” as used herein may refer to any transmissionmedium, either tangible or intangible, which is used to communicate dataor a data stream. Additionally, the term “link” may be synonymous withand/or equivalent to “communications channel,” “data communicationschannel,” “transmission channel,” “data transmission channel,” “accesschannel,” “data access channel,” “channel,” “data link,” “radio link,”“carrier,” “radiofrequency carrier,” and/or any other like term denotinga pathway or medium through which data is communicated.

As used hereinafter, including the claims, the terms “module”“communications module”, “communications circuitry” “communicationsmanagement module,” “control module” “control unit,” “shipmentmanagement module” and/or “multiple RF modules”, may refer to, be partof, or include one or more Application Specific Integrated Circuits(ASIC), electronic circuits, programmable combinational logic circuits(such as field programmable gate arrays (FPGA)) programmed with logic toperform operations described herein, a processor (shared, dedicated, orgroup) and/or memory (shared, dedicated, or group) that execute one ormore software or firmware programs generated from a plurality ofprogramming instructions with logic to perform operations describedherein, and/or other suitable components that provide the describedfunctionality and/or any combination of software, firmware or hardware.

Referring now to FIG. 1, wherein a system for providing transfer ofcustody communications, as well as monitoring for any “lost”sensors/nodes according to the present disclosure, in accordance withvarious embodiments, is illustrated. As shown, system 100 may include agateway 120 provided in a premise, for example a warehouse, a truck, arail car, rolling stock, an airplane, cargo carrying device or vehicle,or other milieu where goods are prepared for transit to a destination,are in transit, or have reached a destination may be located.

Apparatus 120 may be referred to as a Gateway, as shown. For thepurposes of this description, apparatus 120 is designated as the“Current Gateway”, i.e., the gateway to which Sensor/Nodes A through D111-114 are initially assigned. In asset tracking systems, such as maybe included in system 100 of FIG. 1, the sensors/nodes are attached topackages or other units of merchandise, and multiple sensors/nodes areassigned to, and are monitored by, gateways. As described below, each ofSensors/Nodes A through D, 111-114 may have various sensors, and may beimplemented as what is sometimes known as “smart sensors” or “smarttags.” For the purposes of this description, the term “gateway” as usedherein includes any device to which a particular sensor/node isassigned, even for a short time, as in what is known as an“intermediary” or gateway “proxy.” For example, a warehouse may havevarious gateways installed, which monitor sensors on packages or palletsof merchandise. When a new shipment comes into the warehouse on a truck,for example, the merchandise in the truck may generally be monitored by,and thus assigned to, a gateway installed on the truck. Once unloaded,it may be that a first portion of the packages in the truck are to besent onwards to one destination, and a second portion of the packagesothers to a wholly different one. It may also be that when the truckinitially enters the warehouse, the gateways to which each of the firstand second portions of packages are to be assigned to for the next legof their respective journeys may not yet be known, and thus each of theportions may be assigned to a representative or proxy of their actualnext gateway, which will subsequently hand them off to the gateway thatwill monitor them on the next leg of their respective journeys. In somecontexts, a sensor may be known as a “child”, and the gateway to whichit is assigned as its “parent.” In a transfer of custody as describedbelow, one or more “children” are advised that they are now in thecustody of a new “parent.”

Apparatus 120 may be one or more hardware devices and/or one or moresoftware modules and/or any combination of hardware and software thatcarry out the monitoring and communication with Sensor/Nodes A through D111-114 in a premise or venue. In embodiments, the one or more hardwaredevices may be tamper resistant and the operations may be carried outindependent of processor(s) of a host/application platform. Inembodiments where apparatus 120 is implemented as one or more softwaremodules, the software modules may include “enclaves” which may beisolated regions of code and/or data within the memory of a computingplatform.

As seen, in FIG. 1 two Apparatuses 120, 120-1 are shown. Each is agateway to which are assigned, or may be assigned, several sensor nodes.The description of Apparatus 120 is thus identical for that of Apparatus120-1.

Apparatus 120 may communicate with a cloud server 140 of system 100, asdescribed below. In embodiments, apparatus 120 may include aMicrocontroller Unit (MCU) 121, Multiple RF Modules 123, a Battery 125and Supporting Circuitry 127. In embodiments, Multiple RF Modules 123may include WiFi, cellular and Near Field Communication (NFC) modules,and may be implemented in circuitry or communications circuitry ofvarious types. It is noted that MCU 121 may be implemented as a TexasInstruments (TI) CC2630, or the like. Microcontrollers are embeddedcontrollers that perform compute functions at low power and userelatively quicker sleep-wake and wake-sleep timing. In embodiments, MCU121 may also contain the Media Access Control (MAC) layer of thewireless radio. It is noted that the Media Access Control Layer is oneof two sublayers that make up the Data Link Layer of the OSI model. TheMAC layer is responsible for moving data packets to and from one NetworkInterface Card (NIC) to another across a shared channel.

In embodiments, apparatus 120 may communicate with Cloud Server 140 viaUpstream Data Communication Protocol 131, which, in embodiments, asshown, may include a WiFi or cellular connection, or other appropriatecommunications link, and apparatus 120 may communicate withSensors/Nodes 111-114 over wireless connections, using, for example, theIEEE 802.15.4 protocol, or some equivalent protocol, as the case may be.IEEE 802.15.4 is a technical standard which defines the operation oflow-rate wireless personal area networks (LR-WPANs). It specifies thephysical layer and media access control for LR-WPANs, and is maintainedby the IEEE 802.15 working group, which defined the standard in 2003,and published an updated version in 2006, IEEE 802.15.4-2006 (whichsuperceded the 2003 version).

In embodiments, apparatus 120 may communicate wirelessly, via MultipleRF Modules 123 and modem 129, with Sensors/Nodes A through D 111-114disposed in its general physical vicinity. As noted above, Sensors/NodesA through D 111-114 may be smart tags packed inside packages or palletsof merchandise, or attached to them, as the case may be. Each ofSensors/Nodes A through D 111-114 may include a sensor microcontrollerunit (MCU), through which it communicates with apparatus 120, and a setof sensors, such as one or more of a humidity/temperature sensor, a 6Daccelerometer with tilt, an ambient light sensor, or a pressure sensor.Each of Sensors/Nodes A through D 111-114 may also contain a powersource, such as a coin cell battery or the like.

As used herein, and in the claims, sensors assigned to a gateway may besaid to be part of that gateway's network. In that sense, a wirelesssensor network (WSN) includes many such individual gateways, each withits own “network,” where the gateways may communicate with the cloud,and as described herein, with other gateways, and even with the sensorscurrently assigned to another gateway (as described in connection withFIG. 2 below). Thus, in a larger sense, the WSN is all one largenetwork.

Continuing with reference to FIG. 1, in embodiments, each apparatus 120may receive information from the cloud, e.g., from Cloud Asset TrackingServer 140, regarding which sensors or smart tags to hand off to anotherapparatus, such as, for example, informing Current Gateway 120 to handoff custody of some or all of Sensors/Nodes A through D 111-114 to NewGateway 120-1.

Cloud Asset Tracking Server 140 may be one or more hardware devicesand/or one or more software modules that carry out the collection ofdata regarding shipments and individual packages or pallets within thoseshipments, and the tracking of those shipments via data received fromvarious gateways that report to it. In embodiments, the one or morehardware devices may be tamper resistant and the operations may becarried out independent of processor(s) of a host/application platform.In embodiments where apparatus 140 is implemented as one or moresoftware modules, the software modules may include “enclaves” which maybe isolated regions of code and/or data within the memory of a computingplatform.

Cloud Asset Tracking Server 140 may include a Shipment Management Module142, a Communication Management Module 143. Communication ManagementModule 142 may be one or more software modules that operate inconjunction with one or more hardware devices to configurecommunications circuitry (not shown) to communicate with one or moreapparatuses 120. Cloud Asset Tracking Server 140 may include, or may beexpanded to include other module(s), indicated as Other 144 in FIG. 1.

In embodiments, one gateway may communicate with another gateway, suchas apparatus 120 with apparatus 120-1 in FIG. 1, over wireless protocol140, which may be a communications protocol based upon 802.15.4, or anyother wireless technology.

Next described are various processes that may be performed by a currentgateway and a new gateway, according to various embodiments.

As noted above, in embodiments, a reliable, optimum and eleganttechnique to implement a chain of custody transfer of sensors betweenone gateway (GW) to another over a wireless protocol while still intransit or operation, thereby requiring minimal to no manualintervention, may be performed. In embodiments, the periodic beaconsfrom a GW that are primarily used for time synchronization of a network,may be used to propagate custody transfer configuration changes torespective sensor nodes.

Additionally, in embodiments, this may be done effectively by ensuringthat no sensors/nodes are stranded or unassociated from a GW at anypoint in time. In embodiments, these techniques may be implemented in apower optimized manner while still maintaining high reliability and easeof use.

This technique also allows for GW to GW communication which is morereliable while the cloud might be inaccessible. In embodiments, itallows for intelligence to exist more on the edge device rather thanrelying on the cloud for all custody transfer notifications/decisions.

For instance, in most logistics and tracking applications, sensors onspecific packages will need to seamlessly move from, for example, one GWnetwork in a warehouse to another mobile GW network in a truck. Atlocations where the cloud might be inaccessible, this gives the GWsfreedom to make optimum decisions.

Referring now to FIG. 2, an overview of operational flow for a processof transfer of custody of a set of nodes from one GW to the other isillustrated. As illustrated, process 200 may include operationsperformed at blocks 210-250. The operations at blocks 210-250 may beperformed by the various elements of apparatus 120, described earlierwith reference to FIG. 1.

Process 200 may begin at block 210. At block 210 a current gateway mayreceive an instruction from the cloud, such as from Cloud Asset TrackingServer 140, regarding one or more packages or pallets in a shipment thatthe gateway is acting as current gateway for. The instruction may, forexample, direct that a subset of the sensors/nodes currently beingmonitored by the gateway are to be split off of the current shipment andsent to a different destination. That necessitates the smart tags in oron these packages or pallets being placed into the custody of a newgateway in the tracking system, i.e., a transfer of custody from acurrent gateway to a new gateway.

At block 220 the current gateway may notify the new gateway ofadditional sensor/nodes to track, which are the very nodes that arebeing transferred to the custody of the new gateway. In general, it isnoted, this notification may be a custom message that may be defined andtransmitted over any standard/non-standard network socket.

The notification (from the current gateway) to the new gateway at block220 allows the new gateway to send out a specific association beaconthat allows for the new nodes to join its network, and the new nodes maythen respond. In embodiments, the association beacon sent by the newgateway, and the client responses to it, may have the following form:

Association beacon:

AB->ASSOCIATION_BEACON_HEADER_BYTE

0x00->6 bits reserved, 1 bit Calibrate, 1 bit NACK [no calibrate and noNACK in this example]

0x64 0x00->100 max number of clients

0x00->Server beacon time slot to avoid the client from transmitting datawhile the server is transmitting the beacon

0x01 0x01->101 client ID

0x02 0x01->102 client ID

0x03 0x01->103 client ID

0x04 0x01->104 client ID

Client response—Alive message:

0xBB

Alternatively, it is noted, at block 220 the message to the new gatewaymay come from the cloud.

An example of such an association beacon, sent to client IDs 101, 102,103 and 104, and the four resultant client responses, is depicted inFIG. 5A. A magnified view (for easier viewing) of both the associationbeacon and the client responses are shown in FIG. 5B (upper image), anda magnified view of just the payload of the association beacon sent bythe new gateway (lower image). It is noted that the “MAC Payload” refersto a Media Access Control address, a hardware address that uniquelyidentifies each node of a network. In IEEE 802 networks, the Data LinkControl (DLC) layer of the OSI Reference Model is divided into twosub-layers: the Logical Link Control (LLC) layer and the Media AccessControl (MAC) layer. The MAC layer interfaces directly with the networkmedium.

It is further noted that although, in embodiments, the new gateway sendsout this association beacon, in the example messaging of FIGS. 5A and 5Bthe Source Address states “0x0201” which is actually the source addressof the current gateway. The images of FIG. 5A were created to capturethe protocol, and thus not specifically the actual process. As noted, inembodiments, the association beacon of FIG. 5A may be sent by the newgateway.

At block 230 the current gateway may send the new gateway ID and a newchannel ID to the transferred nodes. A new channel ID is crucial toavoid interference from two gateways in close proximity communicating onthe same channel. Therefore to make it reliable, same channels areavoided on two gateways involved in custody transfer.

In embodiments, this may also be done via a beaconing mechanism, suchas, for example, the following beacon which may be sent during custodyhandoff of certain packages/sensor clients from one gateway to theother, typically at way points.

GW and CH change beacon—bit map of specific clients:

AC->CONFIG_BEACON_HEADER_BYTE

0x00->6 bits reserved, 1 bit Calibrate, 1 bit NACK [no calibrate and noNACK in this example]

0x01->applies the config change to specific clients

0x01 0x02->201—Server ID (source)

0x10 0x00 0x00 0x00 0x00 0x00 0x00->Bit map for TDM slot [in this caseit is client ID 0x104]

0x05->5 bytes of data to follow

0x01->CONFIG_TYPE_GATEWAYID_CHANNELID

0x05 0x02->new server/GW ID 205

0x11->new channel ID=0x11

0x05->counter for custody change beacon [starts at 5 and will count downto 1]

An example of such an association beacon is depicted in FIG. 6.

Continuing with reference to FIG. 2, process 200 may move from block 230to block 240, where the current gateway may receive an acknowledgementfrom one or more (in optimal conditions, all) of the transferred nodesto which it signaled in block 230.

It is noted that, in embodiments, if one or more of the transferrednodes does not acknowledge the current gateway's communication at block230, that gateway may raise an alarm, known as a logical alarm. This isshown at block 250, shown in dashed line to indicate that this onlyoccurs in cases where a node to be transferred does not acknowledge thecommunication at block 230.

Thus, in embodiments: (a) the current, or “old” gateway may transmit tothe new gateway the information related to the expected clients thatwill now join the new gateway. This may be done via the cloud, or via agateway-to-gateway ad-hoc communication on a management channel, such asis described above in connection with block 220; (b) the nodesthemselves are communicated with using, for example, embeddedinformation in a beacon, and informed that they are to transfer to thenew gateway. However, it is possible that clients may be faulty (for anynumber of reasons). In such case, the old gateway is not going to get anacknowledgement from the node (to its communication at block 230), whileat the same time the new gateway is waiting for the node to connect(because of condition (a) above, the communication at block 220). As thenode(s) does(do) not respond, the old gateway, using agateway-to-gateway management channel may communicate that a specificnode is not operational and raise the alarm.

Process flow may terminate at block 240, if all nodes acknowledge, or,if one or more do not acknowledge, at block 250.

Referring now to FIG. 3, an overview of operational flow for a processat a new gateway following a transfer of custody from a previous gatewayis illustrated. As illustrated, process 300 may include operationsperformed at blocks 310-350. The operations at blocks 310-350 may beperformed by the various elements of apparatus 120-1 (the New Gateway),described earlier with reference to FIG. 1.

It is noted that by performing the processes shown in FIGS. 2 and 3, aseamless provisioning data hand-off of sensor nodes over the wirelessprotocol while still in transit may be performed. In embodiments, thisallows for a smooth and elegant technique for custody transfersrequiring minimal to no manual intervention.

Process 300 may begin at block 310. At block 310 a new gateway mayreceive a list of new nodes to track. In embodiments, the list may beprovided by the current gateway, as noted in connection with block 210of FIG. 2. As noted above, alternatively, the new gateway may receivethe list directly from the cloud, such as from Cloud Asset TrackingServer 140, in FIG. 1.

At block 320 the new gateway may initiate network discovery. The newgateway, upon receiving the new list of sensors/nodes that it needs totrack (from the current gateway, or alternatively, the cloud, as notedabove), may initiate a network discovery/reconfiguration to ensure thatall nodes, both existing and new, are accounted for. In embodiments,this may change the network structure based on proximity to all thenodes.

At block 325 the new gateway may query whether all nodes assigned to itfor monitoring have checked in. If “Yes” at 325, i.e. all the nodescheck in to the GW during this discovery phase, then process 300 maymove to block 330, where the new gateway moves to managed mode for allnodes.

However, if at 325 the answer is “No”, i.e., certain nodes do not checkin within a stipulated time, process flow may move to block 340, and thenew gateway may inform the cloud of the missing nodes to prompt manualintervention, such as a worker trying to find the nodes assigned to thenew gateway that have not responded to the new gateways networkdiscovery signal. Following such notification, process 300 may move intoa managed mode for those nodes that have responded to the networkdiscovery signal, i.e., the available nodes that are tracked andaccounted for. This ensures that there is no loss of data or nodevisibility at the cloud level.

In embodiments, gateway to gateway communication allows for custodytransfers to be managed at an edge device rather than relying on thecloud. Thus, at times when the cloud is inaccessible, gateway to gatewaycommunication can confirm proper package handoffs between gateways andeven alarm other gateways of certain nodes that have been possiblystranded during the custody transfer due to proximity issues or maybelost due to a battery issue. This allows for quick corrective actions onthe field and can call for manual intervention if at all necessary. Inembodiments, this may be implemented using a gateway to gatewaycommunications protocol, which may be based on IEEE 802.15.4 or anyother wireless technology.

Given that, in embodiments, transfer of custody may be performed solelyby the relevant gateways themselves, in embodiments, each gateway mayimplement orphan node detection. This is illustrated by process 400 inFIG. 4, next described.

As illustrated, process 400 may include operations performed at blocks410-430. The operations at blocks 410-430 may be performed by thevarious elements of apparatus 120 (the Current Gateway), or of apparatus120-1 (the New Gateway), described earlier with reference to FIG. 1.

Process 400 may begin at block 410. At block 410 a gateway may scanthrough all 802.15.4 channels during its down time for a small durationafter it has finished managing its own network. Following such scanning,process flow may move to block 415, where it may be determined if anySOS pings were received from any nodes. Of course, such nodes would notbe assigned to the gateway performing process 400. The scan operationdetects any SOS pings from a “lost” node that has been disconnected fromits original network for an extended duration.

To facilitate the utility of process 400, in embodiments, a client beinglost (i.e., one that missed synchronizing beacons from a gateway towhich it was assigned for a certain time) may prompt the client to sendan SOS on a specific channel which can be received by the variousgateways during their routine scans.

From block 410 process 400 may move to block 415, where it may bequeried if any SOS pings were found or received. If “Yes” at block 415,process flow may move to block 425, where it may be queried if thesensor tag is authentic. If “Yes” at 425, then process flow may move toblock 430, where the gateway may communicate the missing sensor tag tothe cloud.

On the other hand, if “No” at 415, then process 400 may return to block410, where the process may begin again at the next available interval.Similarly, if “No” at block 425, process 400 may return to block 410,where the process may begin again at the next available interval. Thus,in embodiments, once an abandoned node is found by an arbitrary gateway,the cloud is notified and corrective action is taken to track thatorphaned package. Thus, in embodiments, there is a fail-safe, or backupprocess for insuring that following a change of custody transfer, checksare made for any nodes that somehow may slip through the cracks.

Referring now to FIG. 7, wherein a block diagram of a computer devicesuitable for practicing the present disclosure, in accordance withvarious embodiments, is illustrated. Apparatus 120, 120-1, or CloudAsset Tracking Server 140, all shown in FIG. 1, may each be implementedas such a computer device in some embodiments. As shown, computer device700 may include one or more processors 702, memory controller 703, andsystem memory 704. Each processor 702 may include one or more processorcores and/or hardware accelerator 705. An example of hardwareaccelerator 705 may include, but is not limited to, programmed fieldprogrammable gate arrays (FPGA). Memory controller 703 may be any one ofa number of memory controllers known in the art. System memory 704 mayinclude any known volatile or non-volatile memory.

Additionally, computer device 700 may include mass storage device(s) 706(such as solid state drives), input/output device interface 708 (tointerface with various input/output devices, such as, mouse, cursorcontrol, display device (including touch sensitive screen), and soforth) and communication interfaces 710 (such as network interfacecards, modems and so forth). In embodiments, communication interfaces710 may support wired or wireless communication, including near fieldcommunication. The elements may be coupled to each other via system bus712, which may represent one or more buses. In the case of multiplebuses, they may be bridged by one or more bus bridges (not shown).

Each of these elements may perform its conventional functions known inthe art. In particular, system memory 704 and mass storage device(s) 706may be employed to store a working copy and a permanent copy of theexecutable code of the programming instructions of an operating system,one or more applications, Microcontroller Unit 121, Multiple RF Modules123, Supporting Circuitry 127, Shipping Management Module 142,Communication Management Module 143, and/or Other 144, collectivelyreferred to as computing logic 722. Microcontroller Unit 121, MultipleRF Modules 123, Supporting Circuitry 127, Shipping Management Module142, Communication Management Module 143, and/or Other 144 may beconfigured to practice (aspects of) processes 200, 300 and 400 of FIGS.2-4, respectively. The programming instructions may comprise assemblerinstructions supported by processor(s) 702 or high-level languages, suchas, for example, C, that can be compiled into such instructions. Inembodiments, some of computing logic may be implemented in hardwareaccelerator 705.

A permanent copy of the executable code of the programming instructionsor the bit streams for configuring hardware accelerator 705 may beplaced into permanent mass storage device(s) 706 in the factory, or inthe field, through, for example, a distribution medium (not shown), suchas a compact disc (CD), or through communication interface 710 (from adistribution server (not shown)).

The number, capability and/or capacity of these elements 710-712 mayvary, depending on the intended use of example computer device 700.

FIG. 8 illustrates an example computer-readable storage medium havinginstructions configured to implement all (or portion of) MicrocontrollerUnit 121, Multiple RF Modules 123, Supporting Circuitry 127, ShippingManagement Module 142, Communication Management Module 143 and Other144, and/or practice (aspects of) processes 200, 300 and 400 of FIGS.2-4, respectively, earlier described, in accordance with variousembodiments. As illustrated, computer-readable storage medium 802 mayinclude the executable code of a number of programming instructions orbit streams 804. Executable code of programming instructions (or bitstreams) 804 may be configured to enable a device, e.g., computer device800, in response to execution of the executable code/programminginstructions (or operation of an encoded hardware accelerator 705), toperform (aspects of) processes 200, 300 and 400 of FIGS. 2-4,respectively. In alternate embodiments, executable code/programminginstructions/bit streams 804 may be disposed on multiple non-transitorycomputer-readable storage medium 802 instead. In embodiments,computer-readable storage medium 802 may be non-transitory. In stillother embodiments, executable code/programming instructions 804 may beencoded in transitory computer readable medium, such as signals.

Referring back to FIG. 7, for one embodiment, at least one of processors702 may be packaged together with a computer-readable storage mediumhaving some or all of computing logic 722 (in lieu of storing in systemmemory 704 and/or mass storage device 706) configured to practice all orselected ones of the operations earlier described with references toFIGS. 2-4. For one embodiment, at least one of processors 702 may bepackaged together with a computer-readable storage medium having some orall of computing logic 722 to form a System in Package (SiP). For oneembodiment, at least one of processors 702 may be integrated on the samedie with a computer-readable storage medium having some or all ofcomputing logic 722. For one embodiment, at least one of processors 702may be packaged together with a computer-readable storage medium havingsome or all of computing logic 722 to form a System on Chip (SoC). Forat least one embodiment, the SoC may be utilized in, e.g., but notlimited to, a hybrid computing tablet/laptop.

Although certain embodiments have been illustrated and described hereinfor purposes of description, a wide variety of alternate and/orequivalent embodiments or implementations calculated to achieve the samepurposes may be substituted for the embodiments shown and describedwithout departing from the scope of the present disclosure. Thisapplication is intended to cover any adaptations or variations of theembodiments discussed herein. Therefore, it is manifestly intended thatembodiments described herein be limited only by the claims.

Where the disclosure recites “a” or “a first” element or the equivalentthereof, such disclosure includes one or more such elements, neitherrequiring nor excluding two or more such elements. Further, ordinalindicators (e.g., first, second or third) for identified elements areused to distinguish between the elements, and do not indicate or imply arequired or limited number of such elements, nor do they indicate aparticular position or order of such elements unless otherwisespecifically stated.

Illustrative examples of the technologies disclosed herein are providedbelow. An embodiment of the technologies may include any one or more,and any combination of, the examples described below.

Example 1 may include an apparatus for providing for providing transferof custody signaling in a wireless sensor network, comprising:communications circuitry to interact with a cloud server to receive aninstruction regarding a change of custody for at least one sensor nodewithin a wireless sensor network (WSN), wherein the at least one sensornode is assigned to the apparatus for tracking and wherein theinstruction identifies a second apparatus to assume custody of the atleast one sensor, and a control unit coupled to the communicationsmodule to signal the second apparatus and the at least one sensor noderegarding a change of custody for the at least one sensor from theapparatus to the second apparatus; wherein the signaling is over awireless protocol of the WSN.

Example 2 may include the apparatus of example 1, or any other exampleherein, wherein the signaling utilizes periodic beacons that are sentfrom apparatuses in the WSN for time synchronization.

Example 3 may include the apparatus of example 1, or any other exampleherein, wherein the apparatuses in the WSN are each assigned one or moresensor nodes to track.

Example 4 may include the apparatus of any of examples 1-3, or any otherexample herein, wherein the sensor nodes are attached to, or packedwith, packages or pallets of merchandise in transit.

Example 5 may include the apparatus of example 4, or any other exampleherein, wherein the transfer of custody signaling includes notifying thesecond apparatus to assume responsibility of tracking the at least onesensor node.

Example 6 may include the apparatus of example 4, or any other exampleherein, wherein the cloud server is an asset tracking system server.

Example 7 may include the apparatus of example 4, or any other exampleherein, wherein the transfer of custody signaling includes notifying theat least one sensor of a network identification (ID) of the secondapparatus and a channel ID on which to receive beacons from the secondapparatus, the channel ID being different than the channel ID used bythe apparatus.

Example 8 may include the apparatus of example 4, or any other exampleherein, wherein the wireless protocol is based on IEEE 802.15.4.

Example 9 may include the apparatus of either of examples 1 or 8, or anyother example herein, wherein the communications circuitry is tocommunicate in multiple radio frequency (RF) protocols, modalities orbands.

Example 10 may include the apparatus of example 9, or any other exampleherein, wherein the multiple RF protocols include WiFi, cellular andnear-field communication (NFC).

Example 11 may include the apparatus of example 3, or any other exampleherein, wherein the communications module is to further receive anacknowledgement from the at least one sensor node.

Example 12 may include the apparatus of claim 11, or any other exampleherein, wherein if the communications module does not receive theacknowledgement as to a sensor node, the control unit signals the cloudserver that that sensor node is not operational.

Example 13 may include an apparatus for providing transfer of custodysignaling in a wireless sensor network, comprising: communicationscircuitry to interact with one of a second apparatus within the WSN or acloud server to receive an instruction regarding a transfer of custodyfor at least one sensor node within a wireless sensor network (WSN), theinstruction providing that the custody of the at least one sensor nodeis to be transferred from the second apparatus to the apparatus; and acontrol unit coupled to the communications circuitry to, upon receipt ofthe instruction, signal the at least one sensor node to allow the atleast one sensor node to join the apparatus' network, wherein the signalis over a wireless protocol of the WSN.

Example 14 may include the apparatus of example 13, or any other exampleherein, wherein the signal to the at least one sensor is an associationbeacon.

Example 15 may include the apparatus of example 13, or any other exampleherein, wherein the cloud server is an asset tracking system server.

Example 16 may include the apparatus of any of examples 13-15, or anyother example herein, wherein apparatuses in the WSN are each assignedone or more sensor nodes to track.

Example 17 may include the apparatus of example 16, or any other exampleherein, wherein the sensor nodes are attached to, or packed with,packages or pallets of merchandise in transit.

Example 18 may include the apparatus of example 16, or any other exampleherein, wherein the apparatus is to further perform network discoveryfollowing completion of the transfer of custody.

Example 19 may include the apparatus of example 18, or any other exampleherein, wherein completion of transfer of custody includes receiving aresponse from the at least one sensor nodes that were identified in theinstruction.

Example 20 may include the apparatus of example 16, or any other exampleherein, wherein network discovery includes: sending a signal to eachsensor node assigned to the custody of the apparatus; noting whichsensor nodes responded; notifying the cloud server of any missing sensornodes; and moving to managed mode for all sensor nodes that did respond.

Example 21 may include a method to be performed by a computer deviceproviding transfer of custody signaling in a wireless sensor network(WSN), comprising: obtaining or receiving, by the computer device, froma cloud server, an instruction regarding a transfer of custody for atleast one sensor node within a wireless sensor network (WSN), whereinthe at least one sensor node is assigned to the computer device fortracking, and wherein the instruction identifies a second computerdevice within the WSN to assume custody of the at least one sensor node;and

interacting, by the computer device, with the second apparatus and theat least one sensor node to provide transfer of chain of custodysignaling, wherein the signaling is over a wireless protocol of the WSN.

Example 22 may include the method of example 21, or any other exampleherein, wherein the signaling utilizes periodic beacons that are sentfrom apparatuses in the WSN for time synchronization.

Example 23 may include the method of example 21, or any other exampleherein, wherein apparatuses in the WSN are each assigned one or moresensor nodes to track, including to periodically wirelessly communicatewith the sensor nodes.

Example 24 may include the method of any one of examples 21-23, or anyother example herein, wherein the sensor nodes are attached to, orpacked with, packages or pallets of merchandise in transit.

Example 25 may include the method of example 24, or any other exampleherein, wherein the transfer of custody signaling includes notifying thesecond apparatus to assume responsibility of tracking the at least onesensor node.

Example 26 may include the method of example 24, or any other exampleherein, wherein the cloud server is an asset tracking system server.

Example 27 may include the method of example 24, or any other exampleherein, wherein the transfer of custody signaling includes notifying theat least one sensor of a network identification (ID) of the secondapparatus and a channel ID on which to receive beacons from the secondapparatus, the channel ID being different than the channel ID used bythe apparatus.

Example 28 may include the method of example 24, or any other exampleherein, wherein the wireless protocol is based on IEEE 802.15.4.

Example 29 may include the method of example 21, or any other exampleherein, wherein the computer device is to further receive anacknowledgement from the at least one sensor node.

Example 30 may include the method of example 29, or any other exampleherein, wherein if the computer device does not receive theacknowledgement as to a sensor node, the control unit signals the cloudserver that that sensor node is not operational.

Example 31 may include a method to be performed by a computer deviceproviding transfer of custody signaling in a wireless sensor network(WSN), comprising: obtaining or receiving, by the computer device, fromone of a second computer device within the WSN or a cloud server, aninstruction regarding a transfer of custody for at least one sensor nodewithin a wireless sensor network (WSN), the instruction providing thatthe custody of the at least one sensor node is to be transferred fromthe second computer device to the computer device; and interacting, bythe computer device, with the at least one sensor node to signal the atleast one sensor node to allow the at least one sensor node to join theapparatus' network, wherein the signal is over a wireless protocol ofthe WSN.

Example 32 may include the method of example 31, or any other exampleherein, wherein the signal to the at least one sensor is an associationbeacon.

Example 33 may include the method of example 31, or any other exampleherein, wherein the cloud server is an asset tracking system server.

Example 34 may include the method of any of examples 31-33, or any otherexample herein, wherein computer devices in the WSN are each assignedone or more sensor nodes to track.

Example 35 may include the method of example 34, or any other exampleherein, wherein the sensor nodes are attached to, or packed with,packages or pallets of merchandise in transit.

Example 36 may include the method of example 34, or any other exampleherein, further comprising performing network discovery followingcompletion of the transfer of custody.

Example 37 may include the method of example 36, or any other exampleherein, wherein completion of transfer of custody includes receiving aresponse from the at least one sensor nodes that were identified in theinstruction.

Example 38 may include the method of either of examples 36 or 37, or anyother example herein, wherein network discovery includes: sending asignal to each sensor node assigned to the custody of the apparatus;noting which sensor nodes responded; notifying the cloud server of anymissing sensor nodes; and moving to managed mode for all sensor nodesthat did respond.

Example 39 may include one or more non-transitory computer-readablestorage media (CRM) comprising a plurality of instructions that inresponse to being executed cause a computing device to: interact with acloud server to receive an instruction regarding a transfer of custodyfor at least one sensor node within a wireless sensor network (WSN),wherein the at least one sensor node is assigned to the apparatus fortracking and wherein the instruction identifies a second computingdevice within the WSN to assume custody of the at least one sensor; and

signal the second computing device and the at least one sensor noderegarding the transfer of custody, wherein the signaling is over awireless protocol of the WSN.

Example 40 may include the one or more non-transitory computer-readablestorage media of example 39, or any other example herein, wherein thesignaling utilizes periodic beacons that are sent from computing devicesin the WSN for time synchronization.

Example 41 may include the one or more non-transitory computer-readablestorage media of example 39, or any other example herein, wherein thecomputing devices in the WSN are each assigned one or more sensor nodesto track.

Example 42 may include the one or more non-transitory computer-readablestorage media of any of examples 39-41, or any other example herein,wherein the sensor nodes are attached to, or packed with, packages orpallets of merchandise in transit.

Example 43 may include the one or more non-transitory computer-readablestorage media of example 42, or any other example herein, wherein thetransfer of custody signaling includes notifying the second computingdevice to assume responsibility of tracking the at least one sensornode.

Example 44 may include the one or more non-transitory computer-readablestorage media of example 42, or any other example herein, wherein thecloud server is an asset tracking system server.

Example 45 may include the one or more non-transitory computer-readablestorage media of example 42, or any other example herein, wherein thetransfer of custody signaling includes notifying the at least one sensorof a network identification (ID) of the second computing device and achannel ID on which to receive beacons from the second computing device,the channel ID being different than the channel ID used by the computingdevice.

Example 46 may include the one or more non-transitory computer-readablestorage media of example 39, or any other example herein, wherein thewireless protocol is based on IEEE 802.15.4.

Example 47 may include the one or more non-transitory computer-readablestorage media of example 39, or any other example herein, wherein thecommunications module is to further receive an acknowledgement from theat least one sensor node.

Example 48 may include the one or more non-transitory computer-readablestorage media of example 47, or any other example herein, wherein if thecomputing device does not receive the acknowledgement as to a sensornode, the control unit signals the cloud server that that sensor node isnot operational.

Example 49 may include one or more non-transitory computer-readablestorage media (CRM) comprising a plurality of instructions that inresponse to being executed cause a computing device to: obtain orreceive, from one of a second computing device within a WSN or a cloudserver, an instruction regarding a transfer of custody for at least onesensor node within the wireless sensor network (WSN), the instructionproviding that the custody of the at least one sensor node is to betransferred from the second computing device to the computing device;and interacting, by the computing device, with the at least one sensornode to signal the at least one sensor node to allow the at least onesensor node to join the computing device's network, wherein the signalis over a wireless protocol of the WSN.

Example 50 may include the one or more non-transitory computer-readablestorage media of example 49, or any other example herein, wherein thesignal to the at least one sensor is an association beacon.

Example 51 may include the one or more non-transitory computer-readablestorage media of example 49, or any other example herein, wherein thecloud server is an asset tracking system server.

Example 52 may include the one or more non-transitory computer-readablestorage media of any of examples 49-51, or any other example herein,wherein computing devices in the WSN are each assigned one or moresensor nodes to track.

Example 53 may include the one or more non-transitory computer-readablestorage media of example 34, or any other example herein, wherein thesensor nodes are attached to, or packed with, packages or pallets ofmerchandise in transit.

Example 54 may include the one or more non-transitory computer-readablestorage media of example 49, or any other example herein, furthercomprising performing network discovery following completion of thetransfer of custody.

Example 55 may include the one or more non-transitory computer-readablestorage media of example 54, or any other example herein, whereincompletion of transfer of custody includes receiving a response from theat least one sensor nodes that were identified in the instruction.

Example 56 may include the one or more non-transitory computer-readablestorage media of either of examples 54 or 55, or any other exampleherein, wherein network discovery includes: sending a signal to eachsensor node assigned to the custody of the apparatus; noting whichsensor nodes responded; notifying the cloud server of any missing sensornodes; and moving to managed mode for all sensor nodes that did respond.

Example 57 may include an apparatus for computing provided in a wirelesssensor network (WSN), comprising: means for interacting with a cloudserver to receive an instruction regarding a transfer of custody for atleast one sensor node within the WSN, wherein the at least one sensornode is assigned to the apparatus for tracking and wherein theinstruction identifies a second apparatus within the WSN to assumecustody of the at least one sensor; and means for signaling the secondapparatus and the at least one sensor node regarding the transfer ofcustody, the signaling utilizing a wireless protocol of the WSN.

1-30. (canceled)
 31. One or more non-transitory computer-readablestorage media (NTCRM) comprising a plurality of instructions that inresponse to being executed by a processor of an apparatus, cause theapparatus to: interact with one of a second apparatus or a cloud serverto receive a transfer instruction regarding a transfer of custody for atleast one sensor node, the transfer instruction providing that thecustody of the at least one sensor node is to be transferred from thesecond apparatus to the apparatus, and the apparatus is to communicatewith the at least one sensor node over a first channel that is differentfrom a second channel over which the second apparatus communicates withthe at least one sensor node; and upon receipt of the transferinstruction, and in response to it, signal the at least one sensor nodevia one of a plurality of periodic time synchronization beacons to allowthe at least one sensor node to join a local network of the apparatus.32. The NTCRM of claim 31, wherein the cloud server is an asset trackingsystem server.
 33. The NTCRM of claim 31, wherein the apparatuses arepart of a wireless sensor network (WSN) and are each assigned one ormore sensor nodes to track.
 34. The NTCRM of claim 31, wherein the atleast one sensor node is attached to, or packed with, at least onepackage or pallet of merchandise in transit.
 35. The NTCRM of claim 31,wherein the apparatus is further caused to perform network discoveryfollowing completion of the transfer of custody.
 36. The NTCRM of claim35, wherein completion of the transfer of custody includes receiving aresponse from the at least one sensor nodes that were identified in thetransfer instruction.
 37. The NTCRM of claim 35, wherein to performnetwork discovery includes to: send a signal to each sensor nodeassigned to the custody of the apparatus; note which sensor nodesresponded; notify the cloud server of any missing sensor nodes; and moveto managed mode for all sensor nodes that did respond.
 38. A method tobe performed by a computer device providing signaling for transfer ofcustody of sensor nodes in a wireless sensor network (WSN), comprising:interacting, by the computer device, with one of a second computingdevice or a cloud server to receive a transfer instruction regarding atransfer of custody for at least one sensor node, the transferinstruction providing that the custody of the at least one sensor nodeis to be transferred from the second computing device to the computingdevice, and the computing device is to communicate with the at least onesensor node over a first channel that is different from a second channelover which the second computing device communicates with the at leastone sensor node; and upon receipt of the transfer instruction, and inresponse to it, signaling, by the computer device, the at least onesensor node via one of a plurality of periodic time synchronizationbeacons to allow the at least one sensor node to join a local network ofthe computing device.
 39. The method of claim 38, wherein the cloudserver is an asset tracking system server, and the transfer of custodysignaling includes notifying the second computer device to assumeresponsibility of tracking the at least one sensor node.
 40. The methodof claim 38, further comprising notifying, by the computer device, theat least one sensor node of a network identification (ID) of the secondcomputer device and a channel ID on which to receive beacons from thesecond computer device, the channel ID being different than the channelID used by the computer device.
 41. The method of claim 38, furthercomprising receiving, by the computer device, an acknowledgement fromthe at least one sensor node, and in response to not receiving theacknowledgement, signaling the cloud server that the sensor node is notoperational.
 42. A method comprising: associating, by a sensor node,with a first gateway, and joining a first local wireless network of thefirst gateway to be monitored or managed by the first gateway;communicating wirelessly, by the sensor node, with the first gateway,over a first channel to allow the first gateway to monitor or manage thesensor node; receiving, by the sensor node, an association beacon from asecond gateway to associate with the second gateway to transfermonitoring or management of the sensor node from the first gateway tothe second gateway, the association beacon being one of a plurality ofperiodic time synchronization beacons transmitted by the second gateway;associating, by the sensor node, with the second gateway, and joining asecond local wireless network of the first gateway to be monitored ormanaged by the first gateway; and communicating wirelessly, by thesensor node, with the second gateway, over a second channel, differ fromthe first channel, to allow the second gateway to monitor or manage thesensor node.
 43. The method of claim 42, wherein the sensor node and thefirst and second gateways are part of a wireless sensor network (WSN).44. The method of claim 42, wherein the sensor node is attached to, orpacked with, at least one package or pallet of merchandise in transit.45. The method of claim 38, further comprising receiving, by the sensornode, a network identification (ID) of the second gateway and a channelID on which to receive the plurality of periodic time synchronizationbeacons from the second gateway, the channel ID being different than achannel ID used by the first gateway.
 46. The method of claim 38,further comprising sending, by the sensor node, an acknowledgement, tothe second gateway.